Changelog

Security

• Fix incorrect permission checking on multiple API endpoints (GHSA-58x8-3qxw-6hm7)
• Fix incorrect authorship checking when processing some activities (CVE-2024-37903, GHSA-xjvf-fm67-4qc3)
• Fix ongoing streaming sessions not being invalidated when application tokens get revoked (GHSA-vp5r-5pgw-jwqx)
• Update dependencies

Added

• Add yarn version specification to avoid confusion with Yarn 3 and Yarn 4

Changed

• Change preview cards generation to skip unusually long URLs (oneiros)
• Change search modifiers to be case-insensitive (Gargron)
• Change STATSD_ADDR handling to emit a warning rather than crashing if the address is unreachable (timothyjrogers)
• Change PWA start URL from /home to / (ClearlyClaire)

Removed

• Removed dependency on posix-spawn (ClearlyClaire)

Fixed

• Fix scheduled statuses scheduled in less than 5 minutes being immediately published (danielmbrasil)
• Fix encoding detection for link cards (oneiros)
• Fix /admin/accounts/:account_id/statuses/:id for edited posts with media attachments (ClearlyClaire)
• Fix duplicate @context attribute in user archive export (ClearlyClaire)

Upgrade notes

To get the code for v4.2.10, use git fetch && git checkout v4.2.10.

Dependencies

With the exception of Ruby's recommended version, external dependencies have not changed since v4.2.0, the compatible Ruby, PostgreSQL, Node, Elasticsearch and Redis versions are the same, that is:

• Ruby: 3.0 to 3.2
• PostgreSQL: 10 or newer
• Elasticsearch (recommended, for full-text search): 7.x (OpenSearch should also work)
• LibreTranslate (optional, for translations): 1.3.3 or newer
• Redis: 4 or newer
• Node: 16 or newer
• ImageMagick: 6.9.7-7 or newer

Update steps

The following instructions are for updating from 4.2.9.

If you are upgrading directly from an earlier release, please carefully read the upgrade notes for the skipped releases as well, as they often require extra steps such as database migrations.

Non-Docker only:

1. Install dependencies: bundle install and yarn install --frozen-lockfile
2. Restart all Mastodon processes

Using Docker:

1. Restart all Mastodon processes

Changelog

Security

• Fix incorrect permission checking on multiple API endpoints (GHSA-58x8-3qxw-6hm7)
• Fix incorrect authorship checking when processing some activities (CVE-2024-37903, GHSA-xjvf-fm67-4qc3)
• Fix ongoing streaming sessions not being invalidated when application tokens get revoked (GHSA-vp5r-5pgw-jwqx)
• Update dependencies

Changed

• Change preview cards generation to skip unusually long URLs (oneiros)
• Change search modifiers to be case-insensitive (Gargron)
• Change STATSD_ADDR handling to emit a warning rather than crashing if the address is unreachable (timothyjrogers)
• Change PWA start URL from /home to / (ClearlyClaire)

Fixed

• Fix scheduled statuses scheduled in less than 5 minutes being immediately published (danielmbrasil)
• Fix encoding detection for link cards (oneiros)
• Fix /admin/accounts/:account_id/statuses/:id for edited posts with media attachments (ClearlyClaire)

Upgrade notes

To get the code for v4.1.18, use git fetch && git checkout v4.1.18.

Dependencies

External dependencies have not changed compared to v4.1.14, the compatible Ruby, PostgreSQL, Node, Elasticsearch and Redis versions are the same, that is:

• Ruby: 3.0
• PostgreSQL: 9.5 or newer
• Elasticsearch (optional, for full-text search): 7.x
• Redis: 4 or newer
• Node: >= 14, < 18
• ImageMagick: 6.9.7-7 or newer

Update steps

The following instructions are for updating from 4.1.17.

If you are upgrading directly from an earlier release, please carefully read the upgrade notes for the skipped releases as well, as they often require extra steps such as database migrations.

Non-Docker only:

1. Install dependencies: bundle install and yarn install --frozen-lockfile

Both Docker and non-Docker:

1. Restart all Mastodon processes

Changelog

Security

• Update dependencies
• Fix private mention filtering (GHSA-5fq7-3p3j-9vrf)
• Fix password change endpoint not being rate-limited (GHSA-q3rg-xx5v-4mxh)
• Add hardening around rate-limit bypass (GHSA-c2r5-cfqr-c553)

Added

• Add rate-limit on OAuth application registration (ThisIsMissEm)
• Add fallback redirection when getting a webfinger query WEB_DOMAIN@WEB_DOMAIN (ClearlyClaire)
• Add digest attribute to Admin::DomainBlock entity in REST API (ThisIsMissEm)

Removed

• Remove superfluous application-level caching in some controllers (ClearlyClaire)
• Remove aggressive OAuth application vacuuming (ThisIsMissEm)

Fixed

• Fix leaking Elasticsearch connections in Sidekiq processes (ClearlyClaire)
• Fix language of remote posts not being recognized when using unusual casing (ClearlyClaire)
• Fix off-by-one in tootctl media commands (ClearlyClaire)
• Fix removal of allowed domains (in LIMITED_FEDERATION_MODE) not being recorded in the audit log (ThisIsMissEm)
• Fix not being able to block a subdomain of an already-blocked domain through the API (ClearlyClaire)
• Fix Idempotency-Key being ignored when scheduling a post (ClearlyClaire)
• Fix crash when supplying the FFMPEG_BINARY environment variable (timothyjrogers)
• Fix improper email address validation (ClearlyClaire)
• Fix results/query in api/v1/featured_tags/suggestions (mjankowski)
• Fix unblocking internationalized domain names under certain conditions (tribela)
• Fix admin account created by mastodon:setup not being auto-approved (ClearlyClaire)
• Fix reference to non-existent var in CLI maintenance command (mjankowski)

Upgrade notes

To get the code for v4.2.9, use git fetch && git checkout v4.2.9.

Dependencies

With the exception of Ruby's recommended version, external dependencies have not changed since v4.2.0, the compatible Ruby, PostgreSQL, Node, Elasticsearch and Redis versions are the same, that is:

• Ruby: 3.0 to 3.2
• PostgreSQL: 10 or newer
• Elasticsearch (recommended, for full-text search): 7.x (OpenSearch should also work)
• LibreTranslate (optional, for translations): 1.3.3 or newer
• Redis: 4 or newer
• Node: 16 or newer
• ImageMagick: 6.9.7-7 or newer

Update steps

The following instructions are for updating from 4.2.8.

If you are upgrading directly from an earlier release, please carefully read the upgrade notes for the skipped releases as well, as they often require extra steps such as database migrations.

Non-Docker only:

1. Install dependencies: bundle install and yarn install --frozen-lockfile
2. Restart all Mastodon processes

Using Docker:

1. Restart all Mastodon processes

Changelog

Security

• Update dependencies
• Fix private mention filtering (GHSA-5fq7-3p3j-9vrf)
• Fix password change endpoint not being rate-limited (GHSA-q3rg-xx5v-4mxh)
• Add hardening around rate-limit bypass (GHSA-c2r5-cfqr-c553)

Added

• Add fallback redirection when getting a webfinger query WEB_DOMAIN@WEB_DOMAIN (ClearlyClaire)
• Add digest attribute to Admin::DomainBlock entity in REST API (ThisIsMissEm)

Removed

• Remove superfluous application-level caching in some controllers (ClearlyClaire)

Fixed

• Fix leaking Elasticsearch connections in Sidekiq processes (ClearlyClaire)
• Fix language of remote posts not being recognized when using unusual casing (ClearlyClaire)
• Fix off-by-one in tootctl media commands (ClearlyClaire)
• Fix removal of allowed domains (in LIMITED_FEDERATION_MODE) not being recorded in the audit log (ThisIsMissEm)
• Fix not being able to block a subdomain of an already-blocked domain through the API (ClearlyClaire)
• Fix Idempotency-Key being ignored when scheduling a post (ClearlyClaire)
• Fix crash when supplying the FFMPEG_BINARY environment variable (timothyjrogers)
• Fix improper email address validation (ClearlyClaire)
• Fix results/query in api/v1/featured_tags/suggestions (mjankowski)
• Fix unblocking internationalized domain names under certain conditions (tribela)
• Fix admin account created by mastodon:setup not being auto-approved (ClearlyClaire)
• Fix reference to non-existent var in CLI maintenance command (mjankowski)

Upgrade notes

To get the code for v4.1.17, use git fetch && git checkout v4.1.17.

Dependencies

External dependencies have not changed compared to v4.1.14, the compatible Ruby, PostgreSQL, Node, Elasticsearch and Redis versions are the same, that is:

• Ruby: 3.0
• PostgreSQL: 9.5 or newer
• Elasticsearch (optional, for full-text search): 7.x
• Redis: 4 or newer
• Node: >= 14, < 18
• ImageMagick: 6.9.7-7 or newer

Update steps

The following instructions are for updating from 4.1.16.

If you are upgrading directly from an earlier release, please carefully read the upgrade notes for the skipped releases as well, as they often require extra steps such as database migrations.

Non-Docker only:

1. Install dependencies: bundle install and yarn install --frozen-lockfile

Both Docker and non-Docker:

1. Restart all Mastodon processes

Changelog

Added

• Add hourly task to automatically require approval for new registrations in the absence of moderators (ClearlyClaire, ClearlyClaire)
  In order to prevent future abandoned Mastodon servers from being used for spam, harassment and other malicious activity, Mastodon will now automatically switch new user registrations to require moderator approval whenever they are left open and no activity (including non-moderation actions from apps) from any logged-in user with permission to access moderation reports has been detected in a full week.
  When this happens, users with the permission to change server settings will receive an email notification.
  This feature is disabled when EMAIL_DOMAIN_ALLOWLIST is used, and can also be disabled with DISABLE_AUTOMATIC_SWITCHING_TO_APPROVED_REGISTRATIONS=true.

Changed

• Change registrations to be closed by default on new installations (ClearlyClaire)
  If you are running a server and never changed your registrations mode from the default, updating will automatically close your registrations.
  Simply re-enable them through the administration interface or using tootctl settings registrations open if you want to enable them again.

Fixed

• Fix processing of remote ActivityPub actors making use of Link objects as Image url (ClearlyClaire)
• Fix link verifications when page size exceeds 1MB (ClearlyClaire)

Moderation tooling

While we work on better tools to fight spam and abuse, we want to draw your attention to the tools already at your disposal:

• Manual review for new user registrations
• Blocking disposable/temporary e-mail providers (such as any.pink being used in the current wave)
• Setting up hCaptcha

Known issues

When setting up a new server, the admin account created by the mastodon:setup task will not be automatically approved. You will need to approve it from the command-line interface with RAILS_ENV=production bin/tootctl accounts modify <username> --approve.

Upgrade notes

To get the code for v4.2.8, use git fetch && git checkout v4.2.8.

Dependencies

With the exception of Ruby's recommended version, external dependencies have not changed since v4.2.0, the compatible Ruby, PostgreSQL, Node, Elasticsearch and Redis versions are the same, that is:

• Ruby: 3.0 to 3.2
• PostgreSQL: 10 or newer
• Elasticsearch (recommended, for full-text search): 7.x (OpenSearch should also work)
• LibreTranslate (optional, for translations): 1.3.3 or newer
• Redis: 4 or newer
• Node: 16 or newer
• ImageMagick: 6.9.7-7 or newer

Update steps

The following instructions are for updating from 4.2.7.

If you are upgrading directly from an earlier release, please carefully read the upgrade notes for the skipped releases as well, as they often require extra steps such as database migrations.

Non-Docker only:

1. Install dependencies: bundle install and yarn install --frozen-lockfile
2. Precompile the assets: RAILS_ENV=production bundle exec rails assets:precompile
3. Restart all Mastodon processes

Using Docker:

1. Restart all Mastodon processes

Changelog

Added

• Add hourly task to automatically require approval for new registrations in the absence of moderators (ClearlyClaire, ClearlyClaire)
  In order to prevent future abandoned Mastodon servers from being used for spam, harassment and other malicious activity, Mastodon will now automatically switch new user registrations to require moderator approval whenever they are left open and no activity (including non-moderation actions from apps) from any logged-in user with permission to access moderation reports has been detected in a full week.
  When this happens, users with the permission to change server settings will receive an email notification.
  This feature is disabled when EMAIL_DOMAIN_ALLOWLIST is used, and can also be disabled with DISABLE_AUTOMATIC_SWITCHING_TO_APPROVED_REGISTRATIONS=true.

Changed

• Change registrations to be closed by default on new installations (ClearlyClaire)
  If you are running a server and never changed your registrations mode from the default, updating will automatically close your registrations.
  Simply re-enable them through the administration interface or using tootctl settings registrations open if you want to enable them again.

Fixed

• Fix processing of remote ActivityPub actors making use of Link objects as Image url (ClearlyClaire)
• Fix link verifications when page size exceeds 1MB (ClearlyClaire)

Moderation tooling

While we work on better tools to fight spam and abuse, we want to draw your attention to the tools already at your disposal:

• Manual review for new user registrations
• Blocking disposable/temporary e-mail providers (such as any.pink being used in the current wave)
• Setting up hCaptcha

Known issues

When setting up a new server, the admin account created by the mastodon:setup task will not be automatically approved. You will need to approve it from the command-line interface with tootctl modify <username> --approved.

Upgrade notes

To get the code for v4.1.16, use git fetch && git checkout v4.1.16.

Dependencies

External dependencies have not changed compared to v4.1.14, the compatible Ruby, PostgreSQL, Node, Elasticsearch and Redis versions are the same, that is:

• Ruby: 3.0
• PostgreSQL: 9.5 or newer
• Elasticsearch (optional, for full-text search): 7.x
• Redis: 4 or newer
• Node: >= 14, < 18
• ImageMagick: 6.9.7-7 or newer

Update steps

The following instructions are for updating from 4.1.15.

If you are upgrading directly from an earlier release, please carefully read the upgrade notes for the skipped releases as well, as they often require extra steps such as database migrations.

Non-Docker only:

1. Install dependencies: bundle install and yarn install --frozen-lockfile

Both Docker and non-Docker:

1. Restart all Mastodon processes

Changelog

Fixed

• Fix OmniAuth tests and edge cases in error handling (ClearlyClaire, ClearlyClaire)
• Fix new installs by upgrading to the latest release of the nsa gem, instead of a no longer existing commit (mjankowski)

Security

• Fix insufficient checking of remote posts (GHSA-jhrq-qvrm-qr36)

Upgrade notes

To get the code for v4.2.7, use git fetch && git checkout v4.2.7.

Dependencies

With the exception of Ruby's recommended version, external dependencies have not changed since v4.2.0, the compatible Ruby, PostgreSQL, Node, Elasticsearch and Redis versions are the same, that is:

• Ruby: 3.0 to 3.2
• PostgreSQL: 10 or newer
• Elasticsearch (recommended, for full-text search): 7.x (OpenSearch should also work)
• LibreTranslate (optional, for translations): 1.3.3 or newer
• Redis: 4 or newer
• Node: 16 or newer
• ImageMagick: 6.9.7-7 or newer

Update steps

The following instructions are for updating from 4.2.6.

If you are upgrading directly from an earlier release, please carefully read the upgrade notes for the skipped releases as well, as they often require extra steps such as database migrations.

Non-Docker only:

1. Install dependencies: bundle install and yarn install --frozen-lockfile
2. Restart all Mastodon processes

Using Docker:

1. Restart all Mastodon processes

Changelog

Fixed

• Fix OmniAuth tests and edge cases in error handling (ClearlyClaire, ClearlyClaire)

Security

• Fix insufficient checking of remote posts (GHSA-jhrq-qvrm-qr36)

Upgrade notes

To get the code for v4.1.15, use git fetch && git checkout v4.1.15.

Dependencies

External dependencies have not changed compared to v4.1.14, the compatible Ruby, PostgreSQL, Node, Elasticsearch and Redis versions are the same, that is:

• Ruby: 3.0
• PostgreSQL: 9.5 or newer
• Elasticsearch (optional, for full-text search): 7.x
• Redis: 4 or newer
• Node: >= 14, < 18
• ImageMagick: 6.9.7-7 or newer

Update steps

The following instructions are for updating from 4.1.14.

If you are upgrading directly from an earlier release, please carefully read the upgrade notes for the skipped releases as well, as they often require extra steps such as database migrations.

Non-Docker only:

1. Install dependencies: bundle install and yarn install --frozen-lockfile

Both Docker and non-Docker:

1. Restart all Mastodon processes

End of life notice

The 4.0.x branch will not receive any further update after this one.

This means that no further security fix will be made available for this branch, and you will need to update to a more recent version (such as the 4.2.x branch) to receive security fixes.

Changelog

Fixed

• Fix OmniAuth tests and edge cases in error handling (ClearlyClaire, ClearlyClaire)

Security

• Fix insufficient checking of remote posts (GHSA-jhrq-qvrm-qr36)

Upgrade notes

To get the code for v4.0.15, use git fetch && git checkout v4.0.15.

Dependencies

External dependencies have not changed compared to v4.0.14, the compatible Ruby, PostgreSQL, Node, Elasticsearch and Redis versions are the same, that is:

• Ruby: 3.0
• PostgreSQL: 9.5 or newer
• Elasticsearch (optional, for full-text search): 7.x
• Redis: 4 or newer
• Node: >= 14, < 18
• ImageMagick: 6.9.7-7 or newer

Update steps

The following instructions are for updating from 4.0.14.

If you are upgrading directly from an earlier release, please carefully read the upgrade notes for the skipped releases as well, as they often require extra steps such as database migrations.

Non-Docker only:

1. Install dependencies: bundle install and yarn install --frozen-lockfile

Both Docker and non-Docker:

1. Restart all Mastodon processes

End of life notice

The 3.5.x branch will not receive any further update after this one.

This means that no further security fix will be made available for this branch, and you will need to update to a more recent version (such as the 4.2.x branch) to receive security fixes.

Changelog

Fixed

• Fix OmniAuth tests and edge cases in error handling (ClearlyClaire, ClearlyClaire)

Security

• Fix insufficient checking of remote posts (GHSA-jhrq-qvrm-qr36)

Upgrade notes

To get the code for v3.5.19, use git fetch && git checkout v3.5.19.

Dependencies

External dependencies have not changed compared to v3.5.18, the compatible Ruby, PostgreSQL, Node, Elasticsearch and Redis versions are the same, that is:

• Ruby: 3.0
• PostgreSQL: 9.5 or newer
• Elasticsearch (optional, for full-text search): 7.x
• Redis: 4 or newer
• Node: >= 12.22, < 18
• ImageMagick: 6.9.7-7 or newer

Update steps

The following instructions are for updating from 3.5.18.

If you are upgrading directly from an earlier release, please carefully read the upgrade notes for the skipped releases as well, as they often require extra steps such as database migrations.

Non-Docker only:

1. Install dependencies: bundle install and yarn install --frozen-lockfile

Both Docker and non-Docker:

1. Restart all Mastodon processes